AI Prompt Library

Pitch Deck Template
1  Start a chat in ChatGPT, Claude, or Gemini and attach two files from your kit folder: Pitch_Deck_Template_16x9.pptx and Pitch Deck Template Map.txt 2  Copy any prompt below, paste it into the chat, and answer its questions
Built for the SlideStart Pitch Deck Template · 16:9 build, 305 slides (August 2026) · 305 slides mapped with measured word limits · in tools that can run code, deck prompts return the assembled .pptx
Send feedbackopens your mail app — or email team@slidestart.com
Slide 2 of the Pitch Deck Template

One prompt runs the entire build: it interviews you, reads anything you attach, plans the deck from this template's layouts, then writes every slide — and in ChatGPT or Claude, hands back the assembled .pptx.

Investor pitch deck
The classic raise: problem, solution, market, traction, team, the ask.
12–15 slides · interviews you, plans the deck, writes or assembles every slide
Preview prompt
Build me a investor pitch deck using my SlideStart Pitch Deck Template.

I've attached "Pitch Deck Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What does the company do, in one sentence, and what's the round (stage, amount, use of funds)?
2. The problem: who has it, how painful, and what do they do today?
3. Your solution and what makes it 10x better — your names for the product and features?
4. Market size: TAM/SAM/SOM figures you can defend, or the data to derive them?
5. Traction: the honest numbers — revenue, users, growth rate, retention, pipeline?
6. Business model: how you make money, unit economics if you have them?
7. Competition: who else is in the ring, and your durable edge?
8. Team: founders, key hires, and why this team wins?
9. Roadmap: what the money buys over the next 18–24 months?
Finish with three build questions: how many slides (suggest 12–15); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: cover -> problem -> solution -> why now -> market size (TAM/SAM/SOM slide 197 earns its place here) -> product -> traction -> business model -> competition -> team -> roadmap -> the ask. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Click to copy prompt
Build me a investor pitch deck using my SlideStart Pitch Deck Template.

I've attached "Pitch Deck Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What does the company do, in one sentence, and what's the round (stage, amount, use of funds)?
2. The problem: who has it, how painful, and what do they do today?
3. Your solution and what makes it 10x better — your names for the product and features?
4. Market size: TAM/SAM/SOM figures you can defend, or the data to derive them?
5. Traction: the honest numbers — revenue, users, growth rate, retention, pipeline?
6. Business model: how you make money, unit economics if you have them?
7. Competition: who else is in the ring, and your durable edge?
8. Team: founders, key hires, and why this team wins?
9. Roadmap: what the money buys over the next 18–24 months?
Finish with three build questions: how many slides (suggest 12–15); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: cover -> problem -> solution -> why now -> market size (TAM/SAM/SOM slide 197 earns its place here) -> product -> traction -> business model -> competition -> team -> roadmap -> the ask. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Demo day pitch
The 3-minute version: ten slides, one idea per slide, big type.
8–10 slides · one idea per slide, built for a timer
Preview prompt
Build me a demo day pitch using my SlideStart Pitch Deck Template.

I've attached "Pitch Deck Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. One sentence: what do you do and for whom?
2. The single most painful fact about the problem?
3. The demo moment — what does the audience see your product do?
4. Your best traction number and the growth rate behind it?
5. Market size in one defensible figure?
6. The team in one line — the credential that buys belief?
7. The ask — how much, and the one thing it unlocks?
Finish with three build questions: how many slides (suggest 8–10); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: cover -> problem (one stat) -> solution/demo -> traction (one big number) -> market -> team -> the ask. Prefer big-statement layouts: stat cards (211, 212), quote (300), photo features (269, 270). Every slide must survive a 20-second read. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Click to copy prompt
Build me a demo day pitch using my SlideStart Pitch Deck Template.

I've attached "Pitch Deck Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. One sentence: what do you do and for whom?
2. The single most painful fact about the problem?
3. The demo moment — what does the audience see your product do?
4. Your best traction number and the growth rate behind it?
5. Market size in one defensible figure?
6. The team in one line — the credential that buys belief?
7. The ask — how much, and the one thing it unlocks?
Finish with three build questions: how many slides (suggest 8–10); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: cover -> problem (one stat) -> solution/demo -> traction (one big number) -> market -> team -> the ask. Prefer big-statement layouts: stat cards (211, 212), quote (300), photo features (269, 270). Every slide must survive a 20-second read. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Sales / customer pitch
Sell the product, not the company: their problem, your fix, proof, pricing, next step.
10–14 slides · interviews you, plans the deck, writes or assembles every slide
Preview prompt
Build me a sales / customer pitch using my SlideStart Pitch Deck Template.

I've attached "Pitch Deck Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. Who's the customer in the room — role, company, what they care about?
2. Their problem as THEY would describe it, and what it costs them?
3. Your product's fix — the 2–3 capabilities that matter to this buyer?
4. Proof: customers like them, results, testimonials, logos you can show?
5. Pricing or commercial model — what are you proposing?
6. Implementation: how fast to value, what you need from them?
7. The next step you want from this meeting?
Finish with three build questions: how many slides (suggest 10–14); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: their world -> the cost of the problem -> your fix (features mapped to their pains) -> proof (testimonials 291, logos 292, results 211-221) -> pricing/model -> implementation -> next steps (301). Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Click to copy prompt
Build me a sales / customer pitch using my SlideStart Pitch Deck Template.

I've attached "Pitch Deck Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. Who's the customer in the room — role, company, what they care about?
2. Their problem as THEY would describe it, and what it costs them?
3. Your product's fix — the 2–3 capabilities that matter to this buyer?
4. Proof: customers like them, results, testimonials, logos you can show?
5. Pricing or commercial model — what are you proposing?
6. Implementation: how fast to value, what you need from them?
7. The next step you want from this meeting?
Finish with three build questions: how many slides (suggest 10–14); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: their world -> the cost of the problem -> your fix (features mapped to their pains) -> proof (testimonials 291, logos 292, results 211-221) -> pricing/model -> implementation -> next steps (301). Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Partnership pitch
Why the two companies win together: the fit, the model, the plan.
10–12 slides · interviews you, plans the deck, writes or assembles every slide
Preview prompt
Build me a partnership pitch using my SlideStart Pitch Deck Template.

I've attached "Pitch Deck Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. Who's the partner and who's in the room?
2. What each side brings — assets, audience, capability?
3. The joint opportunity: what becomes possible together, sized if you can?
4. The partnership model: commercial structure, who does what?
5. Proof it works: pilots, comparable partnerships, early results?
6. Risks and how they're handled?
7. The proposal — what you want them to agree to?
Finish with three build questions: how many slides (suggest 10–12); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: the shared opportunity -> why the fit is real (Venn 180 or hub 106-108 earn their place here) -> the model -> the plan and milestones -> proof -> the proposal. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Click to copy prompt
Build me a partnership pitch using my SlideStart Pitch Deck Template.

I've attached "Pitch Deck Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. Who's the partner and who's in the room?
2. What each side brings — assets, audience, capability?
3. The joint opportunity: what becomes possible together, sized if you can?
4. The partnership model: commercial structure, who does what?
5. Proof it works: pilots, comparable partnerships, early results?
6. Risks and how they're handled?
7. The proposal — what you want them to agree to?
Finish with three build questions: how many slides (suggest 10–12); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: the shared opportunity -> why the fit is real (Venn 180 or hub 106-108 earn their place here) -> the model -> the plan and milestones -> proof -> the proposal. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Product launch presentation
Introduce the product: the gap, the product, the wow, availability.
10–14 slides · interviews you, plans the deck, writes or assembles every slide
Preview prompt
Build me a product launch presentation using my SlideStart Pitch Deck Template.

I've attached "Pitch Deck Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What's launching, and is this internal, press, customer, or event?
2. The gap it fills — what couldn't people do before?
3. The 3–5 headline capabilities, with your feature names?
4. The wow moment or hero demo?
5. Numbers: performance claims, pricing, dates you can commit to?
6. Who's it for — segments, tiers, availability?
7. The call to action at the end?
Finish with three build questions: how many slides (suggest 10–14); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: the gap -> the reveal -> capabilities (icon columns 12-14 or feature bands 66) -> the wow (photo features 269-270, full-bleed 244) -> pricing and availability -> call to action. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Click to copy prompt
Build me a product launch presentation using my SlideStart Pitch Deck Template.

I've attached "Pitch Deck Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What's launching, and is this internal, press, customer, or event?
2. The gap it fills — what couldn't people do before?
3. The 3–5 headline capabilities, with your feature names?
4. The wow moment or hero demo?
5. Numbers: performance claims, pricing, dates you can commit to?
6. Who's it for — segments, tiers, availability?
7. The call to action at the end?
Finish with three build questions: how many slides (suggest 10–14); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: the gap -> the reveal -> capabilities (icon columns 12-14 or feature bands 66) -> the wow (photo features 269-270, full-bleed 244) -> pricing and availability -> call to action. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Company overview deck
The about-us that travels: what you do, proof, people, footprint.
10–14 slides · interviews you, plans the deck, writes or assembles every slide
Preview prompt
Build me a company overview deck using my SlideStart Pitch Deck Template.

I've attached "Pitch Deck Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What does the company do, and who mostly reads this deck?
2. The company story in three beats — founding, inflection, today?
3. Products or services — the map of what you sell?
4. The numbers that prove scale: customers, revenue band, growth, geography?
5. Flagship customers, partners, or case results you can name?
6. The team and structure worth showing?
7. What should a reader do after the last slide?
Finish with three build questions: how many slides (suggest 10–14); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: who we are -> the story (timeline 131-139) -> what we do -> proof in numbers (KPI walls 211-221) -> customers and logos (291-293) -> footprint (295-298) -> team (284-290) -> contact. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Click to copy prompt
Build me a company overview deck using my SlideStart Pitch Deck Template.

I've attached "Pitch Deck Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What does the company do, and who mostly reads this deck?
2. The company story in three beats — founding, inflection, today?
3. Products or services — the map of what you sell?
4. The numbers that prove scale: customers, revenue band, growth, geography?
5. Flagship customers, partners, or case results you can name?
6. The team and structure worth showing?
7. What should a reader do after the last slide?
Finish with three build questions: how many slides (suggest 10–14); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: who we are -> the story (timeline 131-139) -> what we do -> proof in numbers (KPI walls 211-221) -> customers and logos (291-293) -> footprint (295-298) -> team (284-290) -> contact. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Fundraise update for investors
The existing-investor update: progress vs plan, metrics, asks.
8–12 slides · interviews you, plans the deck, writes or assembles every slide
Preview prompt
Build me a fundraise update for investors using my SlideStart Pitch Deck Template.

I've attached "Pitch Deck Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What period does this cover, and what did the last update promise?
2. The metrics that matter this period — actuals vs plan?
3. Wins worth naming, and the honest misses?
4. Runway and burn — where do the numbers stand?
5. Priorities for the next period?
6. Asks: intros, hires, decisions you need from investors?
Finish with three build questions: how many slides (suggest 8–12); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: headline (one number or claim) -> metrics vs plan (dashboards 216, 219-221) -> wins -> misses and fixes -> runway -> next-period priorities -> asks (301). Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Click to copy prompt
Build me a fundraise update for investors using my SlideStart Pitch Deck Template.

I've attached "Pitch Deck Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What period does this cover, and what did the last update promise?
2. The metrics that matter this period — actuals vs plan?
3. Wins worth naming, and the honest misses?
4. Runway and burn — where do the numbers stand?
5. Priorities for the next period?
6. Asks: intros, hires, decisions you need from investors?
Finish with three build questions: how many slides (suggest 8–12); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: headline (one number or claim) -> metrics vs plan (dashboards 216, 219-221) -> wins -> misses and fixes -> runway -> next-period priorities -> asks (301). Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Internal buy-in pitch
Win the room for a new initiative: the case, the plan, the ask.
10–14 slides · interviews you, plans the deck, writes or assembles every slide
Preview prompt
Build me a internal buy-in pitch using my SlideStart Pitch Deck Template.

I've attached "Pitch Deck Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What are you proposing, and who decides?
2. The problem or opportunity inside the company — sized how?
3. The proposal: what you'd build or change, with your names for it?
4. Cost and resourcing — people, money, time?
5. The return: what improves, by how much, by when?
6. Risks and the honest counterarguments?
7. What decision do you need from this meeting?
Finish with three build questions: how many slides (suggest 10–14); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: the problem priced -> the proposal -> how it works -> the plan (roadmap 141-148) -> cost and return -> risks addressed (pros/cons 174-175) -> the decision asked for. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Click to copy prompt
Build me a internal buy-in pitch using my SlideStart Pitch Deck Template.

I've attached "Pitch Deck Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What are you proposing, and who decides?
2. The problem or opportunity inside the company — sized how?
3. The proposal: what you'd build or change, with your names for it?
4. Cost and resourcing — people, money, time?
5. The return: what improves, by how much, by when?
6. Risks and the honest counterarguments?
7. What decision do you need from this meeting?
Finish with three build questions: how many slides (suggest 10–14); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: the problem priced -> the proposal -> how it works -> the plan (roadmap 141-148) -> cost and return -> risks addressed (pros/cons 174-175) -> the decision asked for. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Accelerator / competition deck
The application deck: tight, complete, and readable without you in the room.
10–12 slides · every slide must work as a pre-read
Preview prompt
Build me a accelerator / competition deck using my SlideStart Pitch Deck Template.

I've attached "Pitch Deck Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. The company in one sentence, and which program or competition is this for?
2. Problem and solution — the two-sentence version of each?
3. Traction and market size — the figures you can defend?
4. Business model in one line?
5. The team and the unfair advantage?
6. What you'd use the program or prize for?
Finish with three build questions: how many slides (suggest 10–12); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: cover -> problem -> solution -> market (197) -> traction -> model -> competition -> team -> ask. Titles must carry the argument alone — this deck is read, not presented. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Click to copy prompt
Build me a accelerator / competition deck using my SlideStart Pitch Deck Template.

I've attached "Pitch Deck Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. The company in one sentence, and which program or competition is this for?
2. Problem and solution — the two-sentence version of each?
3. Traction and market size — the figures you can defend?
4. Business model in one line?
5. The team and the unfair advantage?
6. What you'd use the program or prize for?
Finish with three build questions: how many slides (suggest 10–12); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: cover -> problem -> solution -> market (197) -> traction -> model -> competition -> team -> ask. Titles must carry the argument alone — this deck is read, not presented. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Go-to-market plan
How the product reaches the market: segments, channels, motion, targets.
10–14 slides · interviews you, plans the deck, writes or assembles every slide
Preview prompt
Build me a go-to-market plan using my SlideStart Pitch Deck Template.

I've attached "Pitch Deck Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What's going to market, and who's the audience for this plan?
2. Target segments — who first, who later, and why that order?
3. The motion: sales-led, product-led, partner-led — how does a deal actually happen?
4. Channels and the budget behind each?
5. Pricing and packaging?
6. Targets by quarter — pipeline, revenue, customers?
7. Team and gaps to fill?
Finish with three build questions: how many slides (suggest 10–14); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: the market and segments -> the motion (funnel 120-125 earns its place here) -> channels -> pricing -> targets by quarter (155, 145) -> team and asks. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Click to copy prompt
Build me a go-to-market plan using my SlideStart Pitch Deck Template.

I've attached "Pitch Deck Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What's going to market, and who's the audience for this plan?
2. Target segments — who first, who later, and why that order?
3. The motion: sales-led, product-led, partner-led — how does a deal actually happen?
4. Channels and the budget behind each?
5. Pricing and packaging?
6. Targets by quarter — pipeline, revenue, customers?
7. Team and gaps to fill?
Finish with three build questions: how many slides (suggest 10–14); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: the market and segments -> the motion (funnel 120-125 earns its place here) -> channels -> pricing -> targets by quarter (155, 145) -> team and asks. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Vision & roadmap deck
Where the product is going: the destination, the phases, the proof you'll get there.
8–12 slides · interviews you, plans the deck, writes or assembles every slide
Preview prompt
Build me a vision & roadmap deck using my SlideStart Pitch Deck Template.

I've attached "Pitch Deck Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. Whose roadmap — product, company — and who's the audience?
2. The destination: what's true in 2–3 years that isn't today?
3. The phases or horizons, with your names for them?
4. What ships in each phase — the highlights, not the backlog?
5. The proof you can execute: what already shipped, on time?
6. Dependencies or bets that could move dates?
Finish with three build questions: how many slides (suggest 8–12); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: the destination -> why now -> the phases (roadmap 141-148, or telescope 128-129 for a projection) -> what each phase delivers -> proof of execution -> the bets, named honestly. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Click to copy prompt
Build me a vision & roadmap deck using my SlideStart Pitch Deck Template.

I've attached "Pitch Deck Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. Whose roadmap — product, company — and who's the audience?
2. The destination: what's true in 2–3 years that isn't today?
3. The phases or horizons, with your names for them?
4. What ships in each phase — the highlights, not the backlog?
5. The proof you can execute: what already shipped, on time?
6. Dependencies or bets that could move dates?
Finish with three build questions: how many slides (suggest 8–12); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: the destination -> why now -> the phases (roadmap 141-148, or telescope 128-129 for a projection) -> what each phase delivers -> proof of execution -> the bets, named honestly. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Turn my data or document into a pitch
Attach a spreadsheet, memo, or notes — get a pitch built around them.
reads your files first, then interviews only for what's missing
Preview prompt
Turn the attached material into a presentation using my SlideStart Pitch Deck Template.

I've attached "Pitch Deck Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — READ EVERYTHING I ATTACHED before asking anything. Summarize back in five lines: what the material is, the strongest claims in it, the numbers worth showing, and what's missing for a pitch. Then interview me one question at a time ONLY for the gaps — audience, the decision I need, and any missing numbers.

STEP 2 — PROPOSE THE PLAN. Map my material onto this template: numbers to stat and chart slides (my data feeds the caches, per the map's assembly rules), narrative to the pitch spine, proof to testimonial and logo layouts. Show the numbered plan — slide number and layout name | working action title | one line on contents, marking which content comes from my files vs. the interview — and get my approval.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Click to copy prompt
Turn the attached material into a presentation using my SlideStart Pitch Deck Template.

I've attached "Pitch Deck Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — READ EVERYTHING I ATTACHED before asking anything. Summarize back in five lines: what the material is, the strongest claims in it, the numbers worth showing, and what's missing for a pitch. Then interview me one question at a time ONLY for the gaps — audience, the decision I need, and any missing numbers.

STEP 2 — PROPOSE THE PLAN. Map my material onto this template: numbers to stat and chart slides (my data feeds the caches, per the map's assembly rules), narrative to the pitch spine, proof to testimonial and logo layouts. Show the numbered plan — slide number and layout name | working action title | one line on contents, marking which content comes from my files vs. the interview — and get my approval.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.